Any reason why this crashes:
Trigger("Player 1"){
Conditions:
Memory(12737, Exactly, 0);
Memory(12738, Exactly, 0);
Memory(12734, Exactly, 0);
Memory(12733, Exactly, 0);
Actions:
Set Deaths("Current Player", "Vespene Geyser", Set To, 0);
Set Deaths("Current Player", "Mineral Field (Type 3)", Set To, 0);
Set Deaths("Current Player", "Vespene Tank (Terran Type 1)", Set To, 0);
Set Deaths("Current Player", "Vespene Tank (Terran Type 2)", Set To, 0);
Preserve Trigger();
Comment("");
}
//-----------------------------------------------------------------//and this does not crash:
Trigger("Player 1"){
Conditions:
Deaths("Player 6", "ID: 1061", Exactly, 0);
Deaths("Player 7", "ID: 1061", Exactly, 0);
Deaths("Player 3", "ID: 1061", Exactly, 0);
Deaths("Player 2", "ID: 1061", Exactly, 0);
Actions:
Set Deaths("Current Player", "Vespene Geyser", Set To, 0);
Set Deaths("Current Player", "Mineral Field (Type 3)", Set To, 0);
Set Deaths("Current Player", "Vespene Tank (Terran Type 1)", Set To, 0);
Set Deaths("Current Player", "Vespene Tank (Terran Type 2)", Set To, 0);
Preserve Trigger();
Comment("");
}
//-----------------------------------------------------------------//The memory condition trigger crashes while the regular eud trigger does not even though they detect the exact same memory.
None.
An artist's depiction of an Extended Unit Death
I would guess that the memory condition format has a few bugs to be fixed; I'm assuming you're doing this through the text trigger editor, because the condition in classic trigedit is just a hassle.
If I had to guess, I would say that the memory condition never defines where to start on the table. Of course, if anyone's had any successes using the condition, this entire post is garbage.
Why not just stick to the original EUD format?
Try using starforge. if it works, save one with starforge, and one with memory(), then compare the hex of the triggers.
@roy
Original EUD format isn't useable in scmdraft trigedit, only in classic trigedit. If you try to edit with trigedit, you end up with "invalid unit".
"Parliamentary inquiry, Mr. Chairman - do we have to call the Gentleman a gentleman if he's not one?"
Weird. I opened up starforge and when I try to open up the trigger with the memory condition in it, starforge crashed. So I deleted the trigger and redid the trigger in starforge exactly how it was before, played the map, and it works fine now.
Edit: Figured out what went wrong. If you open up the text editor in scmdraft and compile it will crash starcraft and starforge when you open that trigger up.
The memory condition still fails us! 
Post has been edited 3 time(s), last time on Jun 16 2009, 3:52 pm by Morphling.
None.
I do stuff and thingies... Try widening and reducing the number of small nooks and crannies to correct the problem.
Memory condition works in classic trigedit. But the same condition compiled with text based trigedit causes starcraft to crash after mission briefing. :<
Trigedit, generates the wrong condition code in the chk file, the code is supposed to be 15 for deaths, (see
http://www.staredit.net/wiki/scenario.chk_format ), but instead it is 24, which is an invalid code, thus causing a crash when it is checked
None.
Damnit SI
This is why my map doesn't use EUDs, I'm paranoid about stuff like this happening. I still haven't completely forgiven SI for the last time SCMDraft corrupted my EUD using map.
None.
Anyone know how to contact SI or have access to the source? This would probably be a quick fix, and I know alot of people (including myself really would like to use trigedit along with EUDs).
None.
No and no.
He'll sometimes sign onto MSN (which I have), but in terms of getting bugs fixed faster it's useless.
The biggest grudge I have against SI is not releasing the source actually...
EDIT: My sources tell me that he's on AIM a lot. However having stuff fixed faster by bugging him is useless in my exp.
Also my sources are nagging me to nag him, so I will.
Post has been edited 2 time(s), last time on Jun 17 2009, 10:01 pm by scwizard.
None.
Well it is his program, he has full rights to it and owes us nothing (it is us that owe him). But it is also natural for us to want things.
In the meantime you can open up the chk using winmpq and a hex editor and do a search and replace to fix all memory conditions.
None.
http://www.stormcoast-fortress.net/temp/TrigEdit.rarI take back everything bad I said about you SI, ilu <3
EDIT: He told me to test if this works before spreading it around. But I'm to lazy to. Someone else test it.
None.
I do stuff and thingies... Try widening and reducing the number of small nooks and crannies to correct the problem.
WORKS 4 ME... (no momeory condition related Starcraft crash, if triggers were compiled by trigedit)
now I made the triggers to get the EUD to check if the unit has a movement target destination within a few minutes...
-> 117 & 118 are the units I searched...
SI <3
Today is a big day for Starcraft Mapmaking...
I love you too SI, but note that I loved you before you were so fast with that bug fix
None.
